Skip to main content

Overview of the Architecture

Diagram​

UI Layer (Activities/Fragments) <-> Presenter <-> PresenterImpl <-> Data Sources (Local/Remote)

Chosen Architecture​

The project follows the MVP (Model-View-Presenter) architecture to ensure separation of concerns and scalability.

Why MVP​

  • Clear separation of concerns.
  • Enhances testability as business logic is decoupled from the UI.
  • Simplifies maintenance and scalability.

Key Components and Their Responsibilities​

  • Model

    • Represents the data layer.
    • Handles data operations such as database interactions, API calls, and data processing.

  • View

    • Represents the UI layer (Activities, Fragments).
    • Displays data and handles user interactions.
    • Relies user actions to the Presenter without implementing business logic.

  • Presenter

    • Represents the logic layer.
    • Acts as a middleman between the View and the Model.
    • Fetches data from the Model and updates the View.

Flow of Data​

  • Data Flow

    • User interacts with the View (e.g., clicks a button).
    • The View notifies the Presenter of the user action.
    • The Presenter requests data from the Model.
    • The Model processes the request and returns the data to the Presenter.
    • The Presenter processes the data (if necessary) and updates the View.

  • Example

    • User taps a "Login" button in the View.

    • The View callspresenter.signInOffline(username, password)

    • The Presenter calls model.login(username, password).

    • The Model returns the result, and the Presenter updates the View with success or error messages.